Synchronization and training stage operation

ABSTRACT

A primary device implementing the subject system of link establishment for single pair Ethernet may include at least one processor. The at least one processor may be configured to transmit a first synchronization sequence to a secondary device, detect a second synchronization sequence transmitted by the secondary device, the second synchronization sequence differing from the first synchronization sequence, and after detection of the second synchronization sequence, initiate a training stage, the train stage comprising exchanging training frames with the secondary device. The at least one processor may be further configured to enter a data mode for data transmissions after completion of the training stage, the data transmissions being distinct from the training frames. In the data mode, data may be forward error correction encoded and then scrambled.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation application of U.S. patentapplication Ser. No. 14/795,840, entitled “Synchronization and TrainingStage Operation,” filed Jul. 9, 2015, which claims the benefit of U.S.Provisional Patent Application No. 62/174,455, entitled “LinkEstablishment for Single Pair Ethernet,” filed on Jun. 11, 2015, whichare hereby incorporated by reference in their entirety for all purposes.

TECHNICAL FIELD

The present description relates generally to a link establishment,including link establishment for single pair Ethernet.

BACKGROUND

The Ethernet networking protocol has become one of the most commonnetworking protocols in use today. Due to the wide availability ofEthernet, and its large install base, Ethernet is generally able toprovide a greater cost performance than other networking protocols.Accordingly, there has been a recent demand for implementations ofEthernet interfaces across a wide array of industries. Ethernettransmissions generally transmit data over at least one twisted pair ofwires. A twisted pair of wires, or a “twisted pair,” may refer to a typeof cabling where two conductors of a single circuit are twistedtogether. Single pair Ethernet may refer to Ethernet transmissions overa single twisted pair of wires.

Some single pair Ethernet applications, such as automotive Ethernet overunbalanced and unshielded twisted pair cables, may be subject to severenoise degradations, such as from narrow-band interference and/orunpredictable burst noises. The noise degradations may cause corruptionsduring link synchronization and/or training. Corruptions during linksynchronization and/or training may result in unrecoverable errors, suchas failure to detect a link partner or to initialize a scrambler, and/ormay result in corrupted synchronization/training messages that requireretransmissions and thereby lengthen the link establishment time.

BRIEF DESCRIPTION OF THE DRAWINGS

Certain features of the subject technology are set forth in the appendedclaims. However, for purpose of explanation, several embodiments of thesubject technology are set forth in the following figures.

FIG. 1 illustrates an example network environment in which linkestablishment for single pair Ethernet may be implemented in accordancewith one or more implementations.

FIG. 2 illustrates an example electronic device that may implement linkestablishment for single pair Ethernet in accordance with one or moreimplementations.

FIG. 3 illustrates a flow diagram of an example process of linkestablishment for single pair Ethernet in accordance with one or moreimplementations.

FIG. 4 illustrates a flow diagram of an example process of a primaryelectronic device in a synchronization stage of link establishment forsingle pair Ethernet in accordance with one or more implementations.

FIG. 5 illustrates a flow diagram of an example process of a secondaryelectronic device in a synchronization stage of link establishment forsingle pair Ethernet in accordance with one or more implementations.

FIG. 6 illustrates an example primary device synchronization sequencegenerator in accordance with one or more implementations.

FIG. 7 illustrates an example secondary device synchronization sequencegenerator in accordance with one or more implementations.

FIG. 8 illustrates a flow diagram of an example process of a primaryelectronic device in a training stage of link establishment for singlepair Ethernet in accordance with one or more implementations.

FIG. 9 illustrates a flow diagram of an example process of a secondaryelectronic device in a training stage of link establishment for singlepair Ethernet in accordance with one or more implementations.

FIG. 10 illustrates an example timing diagram for link establishment forsingle pair Ethernet in accordance with one or more implementations.

FIG. 11 illustrates an example frame format for a training stage of linkestablishment for single pair Ethernet in accordance with one or moreimplementations.

FIG. 12 illustrates example information field formats for a trainingstage of link establishment for single pair Ethernet in accordance withone or more implementations.

FIG. 13 illustrates a table of example information field messageidentifier values transmitted by a primary electronic device during atraining stage of link establishment for single pair Ethernet inaccordance with one or more implementations.

FIG. 14 illustrates a table of example information field messageidentifier values transmitted by a secondary electronic device during atraining stage of link establishment for single pair Ethernet inaccordance with one or more implementations.

FIG. 15 illustrates an example bit ordering of a physical codingsublayer (PCS) transmit module in accordance with one or moreimplementations.

FIG. 16 further illustrates an example bit ordering of a physical codingsublayer (PCS) transmit module in accordance with one or moreimplementations.

FIG. 17 illustrates an example bit ordering of a physical codingsublayer (PCS) receive module in accordance with one or moreimplementations.

FIG. 18 conceptually illustrates an electronic system with which one ormore implementations of the subject technology may be implemented.

DETAILED DESCRIPTION

The detailed description set forth below is intended as a description ofvarious configurations of the subject technology and is not intended torepresent the only configurations in which the subject technology may bepracticed. The appended drawings are incorporated herein and constitutea part of the detailed description. The detailed description includesspecific details for the purpose of providing a thorough understandingof the subject technology. However, the subject technology is notlimited to the specific details set forth herein and may be practicedusing one or more implementations. In one or more instances, structuresand components are shown in block diagram form in order to avoidobscuring the concepts of the subject technology.

FIG. 1 illustrates an example network environment 100 in which linkestablishment for single pair Ethernet may be implemented in accordancewith one or more implementations. Not all of the depicted components maybe required, however, and one or more implementations may includeadditional components not shown in the figure. Variations in thearrangement and type of the components may be made without departingfrom the spirit or scope of the claims as set forth herein. Additionalcomponents, different components, or fewer components may be provided.

The example network environment 100 includes a number of electronicdevices 102A-C that are coupled to an electronic device 102D viatransmission lines 108. The electronic device 102D may communicablycouple the electronic devices 102A-C to one another. In one or moreimplementations, one or more of the electronic devices 102A-C arecommunicatively coupled directly to one another, such as without thesupport of the electronic device 102D. In one or more implementations,one or more of the transmission lines 108 are Ethernet transmissionlines, such as one or more twisted pairs of wires. The electronic device102D may be, or may include, a switch device, a routing device, a hubdevice, or generally any device that may communicably couple theelectronic devices 102A-C. One or more of the electronic devices 102A-Dmay be, and/or may include all or a portion of, the electronic system1800 discussed below with respect to FIG. 18.

In one or more implementations, at least a portion of the examplenetwork environment 100 is implemented within a vehicle, such as apassenger car. For example, the electronic devices 102A-D may include,and/or may be coupled to, various systems within a vehicle, such as apowertrain system, a chassis system, a telematics system, anentertainment system, a camera system, a sensor system, such as a lanedeparture system, a diagnostics system, or generally any system that maybe used in a vehicle. In FIG. 1, the electronic devices 102A aredepicted as camera devices, such as forward-view, rear-view andside-view cameras, the electronic device 102B is depicted as a sensor,the electronic devices 102C are depicted as entertainment systems, andthe electronic device 102D is depicted as a switch device that mayinclude and/or may be coupled to a central on-board diagnostics system.In one or more implementations, one or more of the electronic devices102A-D may be communicatively coupled to a public communication network,such as the Internet.

The electronic devices 102A-D each implements a physical layer (PHY)that is interoperable with one or more aspects of one or more physicallayer specifications, such as those described in the Institute ofElectrical and Electronics Engineers (IEEE) 802.3 Standards (e.g., 802.3bp). One or more of the electronic devices 102A-D, such as theelectronic device 102D may be configured to operate as a primary (or“master”) device, and one or more of the remaining electronic devices102A-C, such as the electronic device 102A, may be configured to operateas a secondary (or “slave”) device. A primary device provides referenceclock timing in the system while the secondary devices need to recoverthe clock frequency from the primary device. For explanatory purposes,the electronic device 102D is primarily described herein as beingconfigured as a primary device, and the electronic device 102A isprimarily described herein as being configured as a secondary device.However, one or more of the other electronic devices 102A-C may beconfigured as the primary device, and the electronic device 102D may beconfigured as a secondary device.

In operation, a primary electronic device 102D may initiate a linkestablishment with a secondary electronic device 102A, such as across asingle twisted pair of wires, e.g. single pair Ethernet. The electronicdevices 102A,D perform a synchronization stage and a training stage toestablish the link over single pair Ethernet, and then the electronicdevices 102A,D enter a data mode for data transmissions. The linkestablishment is discussed further below with respect to FIGS. 3-14 andthe subsequent data mode is discussed further below with respect toFIGS. 15-17.

FIG. 2 illustrates an example electronic device 102D that may implementlink establishment for single pair Ethernet in accordance with one ormore implementations. Not all of the depicted components may berequired, however, and one or more implementations may includeadditional components not shown in the figure. Variations in thearrangement and type of the components may be made without departingfrom the spirit or scope of the claims as set forth herein. Additionalcomponents, different components, or fewer components may be provided.

The example electronic device 102D includes a media access control (MAC)module 210, a physical layer (PHY) module 220, and a medium dependentinterface (MDI) 260. The PHY module 220 includes a physical codingsublayer (PCS) transmit (Tx) module 230, a PCS receive (Rx) module 240,and a physical medium attachment (PMA) module 250. In one or moreimplementations, the PCS Tx module 230 and the PCS Rx module 240 may becombined in a single PCS module. The PCS Tx module 230 includes a PCSencoder 232, a Reed Solomon (RS) encoder 234 (e.g. 450, 406, m=9), ascrambler 236, and a signal mapper 238. The PCS Rx module 240 includes aPCS decoder 242, an RS decoder 244, a descrambler 246, and a signaldemapper 248. The RS encoder 234 and RS decoder 244 may also be referredto as a forward error correction (FEC) encoder and decoder,respectively.

The MAC module 210 is communicatively coupled to the PHY module 220 viaan interface, such as a gigabit medium independent interface (GMII), orany other interface, over which data is communicated between the MACmodule 210 and the PHY module 220. The PCS encoder 232 performs one ormore encoding and/or transcoding functions on data received from the MACmodule 210, such as 80 b/81 b line encoding. The RS encoder 234 performsRS encoding on the data received from the PCS encoder 232. The scrambler236 is an additive or synchronous scrambler such that bit errors willnot result in descrambler re-synchronization, as may be the case formultiplicative scramblers. The scrambler 236 is placed after the RSencoder 234 and scrambles the RS encoded data by performing anexclusive-or (XOR) operation on the RS encoded data and a scramblingsequence. In one or more implementations, the scrambler 236 is alwaysenabled throughout normal data mode, low power idle mode (while the RSencoder 234 is active), and low power idle refresh mode (when the RSencoder 234 is inactive). In the LPI refresh mode, the referencescrambler sequence can be regenerated for improved performance. Thesignal mapper 238 maps the scrambled data to symbols, such as by mapping3-bits to 2-ternary PAM symbols (3B/2T), or generally any bit to symbolmapping. The symbols are then passed to the PMA module 250.

The PMA module 250 performs one or more functions to facilitateuncorrupted data transmission, such as adaptive equalization, echoand/or crosstalk cancellation, automatic gain control (AGC), etc. TheMDI 260 provides an interface from the PHY module 220 to the physicalmedium used to carry the data, e.g. the transmission lines 108, to thesecondary electronic device 102A. The bit ordering used for the PCS Txmodule 230 is discussed further below with respect to FIGS. 15 and 16.

The PMA module 250 receives symbols transmitted over the transmissionlines 108, e.g. from the secondary electronic device 102A, via the MDI260 and provides the symbols to the PCS Rx module 240. The signaldemapper 248 maps the symbols to scrambled bits, such as by demapping3-bits from 2-ternary PAM symbols. The descrambler 246 descrambles thescrambled bits using scrambler synchronization information received fromthe secondary electronic device 102A, such as a scrambler seed that wasprovided by the secondary electronic device 102A during the trainingstage. The RS decoder 244 performs RS decoding on the descrambled data,and the PCS decoder 242 performs one or more decoding and/or transcodingfunctions on data received from the RS decoder 244, such as 80 b/81 bline decoding. The PCS decoder 242 transmits the decoded data to the MACmodule 210. The bit ordering used for the PCS Rx module 240 is discussedfurther below with respect to FIG. 17.

In one or more implementations, one or more of the MAC module 210, thePHY module 220, the PCS Tx module 230, the PCS encoder 232, the RSencoder 234, the scrambler 236, the signal mapper 238, the PCS Rx module240, the PCS decoder 242, the RS decoder 244, the descrambler 246, thesignal demapper 248, the PMA module 250, the MDI 260, or one or moreportions thereof, may be implemented in software (e.g., subroutines andcode), may be implemented in hardware (e.g., an Application SpecificIntegrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), aProgrammable Logic Device (PLD), a controller, a state machine, gatedlogic, discrete hardware components, or any other suitable devices)and/or a combination of both.

FIG. 3 illustrates a flow diagram of an example process of linkestablishment for single pair Ethernet in accordance with one or moreimplementations. For explanatory purposes, the example process 300 isdescribed herein with reference to the electronic devices 102A,D of FIG.1; however, the example process 300 is not limited to the electronicdevices 102A,D of FIG. 1, and the example process 300 may be performedby one or more components of one or more of the electronic devices102A,D. Further for explanatory purposes, the blocks of the exampleprocess 300 are described herein as occurring in serial, or linearly.However, multiple blocks of the example process 300 may occur inparallel. In addition, the blocks of the example process 300 need not beperformed in the order shown and/or one or more of the blocks of theexample process 300 need not be performed.

The link establishment for single pair Ethernet is initiated when thePHY is enabled for one or more of the primary and secondary electronicdevices 102A,D, such as the PHY module 220 of the primary electronicdevice 102D (302). If the electronic devices 102A,D are configured forautonegotiation (304), the electronic devices 102A,D initiate andperform the autonegotiation, e.g. using differential Manchester encoding(DME) (306). If the electronic devices 102A,D are not configured forautonegotiation (304), the electronic devices 102A,D initiate andperform the synchronization/detection stage of the subject system forlink establishment for single pair Ethernet (308). The synchronizationstage provides a fast and robust synchronization that supports multipletimers, including a link_fail_inhibit_timer and a maxwait_timer. In oneor more implementations, the primary/secondary device assignments arepre-configured for the synchronization stage.

In the synchronization stage (308), the electronic devices 102A,Dutilize synchronization sequences, e.g. special periodic PAM2 sequencesand/or pseudo-noise sequences with strong correlationproperties/characteristics, to ensure detection under the worst casenarrow-band interference and/or burst noise conditions. For example, theelectronic devices 102A,D each transmits its own 255-state pseudo-noise(PN) sequence based on its own eighth degree polynomial according to thepreconfigured primary/secondary device assignments for thesynchronization stage. The electronic devices 102A,D may utilize matchedfilter-based correlators for PN sequence detection. The synchronizationstage (308) is discussed further below with respect to FIGS. 4-7.

Once the synchronization stage (308), or the autonegotiation (306), iscompleted, the primary electronic device 102D initiates the trainingstage (310), e.g. a PAM2 training stage, and the electronic devices102A,D transition through PAM2 states based on message exchanges and/orpartial Reed-Solomon frame (PFC) counts. Once both of the electronicdevices 102A,D have converged their respective receivers, the electronicdevices 102A,D exchange scrambler initialization information, such asscrambler seed/state information. The electronic devices 102A,D alsoexchange data mode timing information that indicates the times that theywill initialize their respective scramblers and switch to the data mode.Thus, based on the exchanged timing information, the electronic devices102A,D may synchronize their scramblers and enter the data modesynchronously. The training stage is discussed further below withrespect to FIGS. 8-14.

After completing the training stage (310) and switching to data mode(312), the electronic devices 102A,D perform Reed-Solomon (RS) forwarderror correction (FEC) encoding on data to be transmitted andsubsequently scramble the encoded data, e.g. using the scramblersinitialized during the training stage (310). The electronic devices102A,D descramble received data, using their respective descramblersinitialized with the other device's scrambler initializationinformation, and then perform RS decoding on the descrambled data. Thedata mode is discussed further below with respect to FIGS. 15-17.

FIG. 4 illustrates a flow diagram of an example process 400 of a primaryelectronic device 102D in a synchronization stage of link establishmentfor single pair Ethernet in accordance with one or more implementations.For explanatory purposes, the example process 400 is primarily describedherein with reference to the electronic device 102D of FIGS. 1-2;however, the example process 400 is not limited to the electronic device102D of FIGS. 1-2, and the example process 400 may be performed by oneor more components of the electronic device 102D. Further forexplanatory purposes, the blocks of the example process 400 aredescribed herein as occurring in serial, or linearly. However, multipleblocks of the example process 400 may occur in parallel. In addition,the blocks of the example process 400 need not be performed in the ordershown and/or one or more of the blocks of the example process 400 neednot be performed.

Upon entering the synchronization stage, the primary electronic device102D transmits its primary device synchronization sequence (402). Theprimary device synchronization sequence is based on a wideband PAM-2pseudo-noise (PN) sequence, such as a PN sequence with a period of 255(2⁸−1) and generally has a good/strong autocorrelation characteristic.The primary device synchronization sequence is specific to the primaryelectronic device 102D and is generated using an eighth degreepolynomial that is specific to the primary electronic device 102D, suchas g_(P)(x)=1+x²+x³+x⁴+x⁸. An example primary device synchronizationsequence generator is discussed further below with respect to FIG. 6.

After transmitting the primary device synchronization sequence (402),the primary electronic device 102D transmits zeros, e.g. packets with nodata, and initiates a detect timer (406). If the primary electronicdevice 102D does not detect the secondary device synchronizationsequence prior to the detect timer reaching a timeout value (406), suchas 4 microseconds, the primary electronic device 102D retransmits theprimary device synchronization sequence (402), restarts the detect timerand continues transmitting zeros (404). In one or more implementations,the primary electronic device 102D may utilize a matched filter-basedcorrelator to detect the secondary device synchronization sequence. Ifthe primary electronic device 102D detects the secondary devicesynchronization sequence prior to the detect timer reaching the timeoutvalue (406), the primary electronic device 102D continues to transmitzeros until the primary electronic device 102D no longer detects thesecondary device synchronization sequence, e.g. until transmission ofthe secondary device synchronization sequence is completed by thesecondary electronic device 102A (408).

The primary electronic device 102D then transmits zeros for apreconfigured duration of time that is pre-shared, or otherwise knownby, the secondary electronic device 102A, such as a duration of fourmicroseconds (410). The secondary electronic device 102A also transmitszeros for the preconfigured duration of time, such that both electronicdevices 102A,D enter the training stage synchronously (412).

FIG. 5 illustrates a flow diagram of an example process 500 of asecondary electronic device 102A in a synchronization stage of linkestablishment for single pair Ethernet in accordance with one or moreimplementations. For explanatory purposes, the example process 500 isprimarily described herein with reference to the electronic device 102Aof FIG. 1; however, the example process 500 is not limited to theelectronic device 102A of FIG. 1, and the example process 500 may beperformed by one or more components of the electronic device 102A.Further for explanatory purposes, the blocks of the example process 500are described herein as occurring in serial, or linearly. However,multiple blocks of the example process 500 may occur in parallel. Inaddition, the blocks of the example process 500 need not be performed inthe order shown and/or one or more of the blocks of the example process500 need not be performed.

Upon entering the synchronization stage, the secondary electronic device102A transmits zeros, e.g. packets with no data (502). If the secondaryelectronic device 102A does not detect the primary devicesynchronization sequence transmitted by the primary electronic device102D (504), the secondary electronic device 102A continues to transmitzeros (502). If the secondary electronic device 102A detects the primarydevice synchronization sequence transmitted by the primary electronicdevice 102D (504), the secondary electronic device 102A transmits zerosuntil the secondary electronic device 102A no longer detects the primarydevice synchronization sequence, e.g. until transmission of the primarydevice synchronization sequence is completed by the primary electronicdevice 102D (506). In one or more implementations, the secondaryelectronic device 102A may utilize a matched filter-based correlator todetect the primary device synchronization sequence.

When the transmission of the primary device synchronization sequence iscomplete (506), the secondary electronic device 102A transmits itssecondary device synchronization sequence to the primary electronicdevice 102D (508). The secondary device synchronization sequence isbased on a wideband PAM-2 pseudo-noise (PN) sequence, such as a PNsequence with a period of 255 (2⁸−1) and generally has a good/strongautocorrelation characteristic. The secondary device synchronizationsequence is specific to the secondary electronic device 102A, i.e. isnot the same as the primary device synchronization sequence, and isgenerated using an eighth degree polynomial that is specific to thesecondary electronic device 102A, such as g_(S)(x)=1+x⁴+x⁵+x⁶+x⁸. Anexample secondary device synchronization sequence generator is discussedfurther below with respect to FIG. 7.

Upon completing transmission of the secondary device synchronizationsequence, the secondary electronic device 102A transmits zeros for apreconfigured duration of time that is pre-shared, or otherwise knownby, the primary electronic device 102D, such as a duration of fourmicroseconds (510). As discussed above, the primary electronic device102D also transmits zeros for the preconfigured duration of time, suchthat both electronic devices 102A,D enter the training stagesynchronously (512).

FIG. 6 illustrates an example primary device synchronization sequencegenerator 600 in accordance with one or more implementations. Not all ofthe depicted components may be required, however, and one or moreimplementations may include additional components not shown in thefigure. Variations in the arrangement and type of the components may bemade without departing from the spirit or scope of the claims as setforth herein. Additional components, different components, or fewercomponents may be provided.

The primary device synchronization sequence generator 600 is illustratedin FIG. 6 as including a linear feedback shift register with taps afterthe second bit (Scr_(n)[1]), the third bit (Scr_(n)[2]), and the fourthbit (Scr_(n)[3]). Thus, the polynomial representation of the linearfeedback shift register of the primary device synchronization sequencegenerator 600 is g_(P)(x)=1+x²+x³+x⁴+x⁸. Thus, the primary devicesynchronization sequence has strong autocorrelation characteristics andcan be detected by the secondary electronic device 102A even under theworst case narrow band interference (NBI) or burst noise conditions. Theoutput (Scr_(n)[0]) of the primary device synchronization sequencegenerator 600 is passed to the signal mapper 238. The signal mapper 238maps the output to a PAM-2 signal. For example, an Scr_(n)[0] value of 0may be mapped to +1 and an Scr_(n)[0] value of 1 may be mapped to −1.

FIG. 7 illustrates an example secondary device synchronization sequencegenerator 700 in accordance with one or more implementations. Not all ofthe depicted components may be required, however, and one or moreimplementations may include additional components not shown in thefigure. Variations in the arrangement and type of the components may bemade without departing from the spirit or scope of the claims as setforth herein. Additional components, different components, or fewercomponents may be provided.

The secondary device synchronization sequence generator 700 isillustrated in FIG. 7 as including a linear feedback shift register withtaps after the fourth bit (Scr_(n)[3]), the fifth bit (Scr_(n)[4]), andthe sixth bit (Scr_(n)[5]). Thus, the polynomial representation of thelinear feedback shift register of the secondary device synchronizationsequence generator 700 is g_(S)(x)=1+x⁴+x⁵+x⁶+x⁸. Thus, the primarydevice synchronization sequence has strong autocorrelationcharacteristics and can be detected by the primary electronic device102D even under the worst case narrow band interference (NBI) or burstnoise conditions. The output (Scr_(n)[0]) of the secondary devicesynchronization sequence generator 700 is passed to the signal mapper238. The signal mapper 238 maps the output to a PAM-2 signal. Forexample, an Scr_(n)[0] value of 0 may be mapped to +1 and an Scr_(n)[0]value of 1 may be mapped to −1.

FIG. 8 illustrates a flow diagram of an example process 800 of a primaryelectronic device 102D in a training stage of link establishment forsingle pair Ethernet in accordance with one or more implementations. Forexplanatory purposes, the example process 800 is described herein withreference to the electronic device 102D of FIGS. 1-2; however, theexample process 800 is not limited to the electronic device 102D ofFIGS. 1-2, and the example process 800 may be performed by one or morecomponents of the electronic device 102D. Further for explanatorypurposes, the blocks of the example process 800 are described herein asoccurring in serial, or linearly. However, multiple blocks of theexample process 800 may occur in parallel. In addition, the blocks ofthe example process 800 need not be performed in the order shown and/orone or more of the blocks of the example process 800 need not beperformed.

Upon entering the training stage, the primary electronic device 102Dtransmits a training sequence, such as one or more PAM2 training frames,to the secondary electronic device 102A (810). The training sequence mayutilize, for example, the training frame format discussed further belowwith respect to FIG. 11, the information field formats discussed furtherbelow with respect to FIG. 12, and/or the primary electronic device 102Dmessage identifier values discussed further below with respect to FIG.13. The primary electronic device 102D receives a training sequence fromthe secondary electronic device 102A (812). The received trainingsequence may utilize the aforementioned formats and/or the secondaryelectronic device 102A message identifier values discussed further belowwith respect to FIG. 14.

The primary electronic device 102D waits for the convergence of itsreceiver (indicating the same to the secondary electronic device 102Avia the aforementioned training sequence), and waits for a trainingframe indicating that the receiver of the secondary electronic device102A has been converged (814). The primary electronic device 102Dtransmits a training frame that includes scrambler initializationinformation for the scrambler 236 of the primary electronic device 102D,such as a scrambler seed, and another training frame that includes datamode timing information indicating a time that the primary electronicdevice 102D will initialize the scrambler 236 and enter the data mode(816).

The primary electronic device 102D receives a training frame from thesecondary electronic device 102A that includes scrambler initializationinformation for the scrambler of the secondary electronic device 102A,such as a scrambler seed, and another training frame that includessecondary device data mode timing information indicating a time that thesecondary electronic device 102A will initialize its scrambler and enterthe data mode (818). The primary electronic device 102D initializes thescrambler 236 with the primary device scrambler initializationinformation at the indicated time and switches to the data mode (820).The primary electronic device 102D initializes the descrambler 246 withthe received secondary device scrambler initialization information atthe time indicated by the secondary electronic device 102A (822). Theprimary electronic device 102D transmits and receives data with thesecondary electronic device 102A using the initialized scrambler 236 anddescrambler 246 (824).

FIG. 9 illustrates a flow diagram of an example process of a secondaryelectronic device 102A in a training stage of link establishment forsingle pair Ethernet in accordance with one or more implementations. Forexplanatory purposes, the example process 900 is described herein withreference to the electronic device 102A of FIG. 1; however, the exampleprocess 900 is not limited to the electronic device 102A of FIG. 1, andthe example process 900 may be performed by one or more components ofthe electronic device 102A. Further for explanatory purposes, the blocksof the example process 800 are described herein as occurring in serial,or linearly. However, multiple blocks of the example process 800 mayoccur in parallel. In addition, the blocks of the example process 800need not be performed in the order shown and/or one or more of theblocks of the example process 800 need not be performed.

Upon entering the training stage, the secondary electronic device 102Atransmits zeros (902) until a training frame, or sequence, is receivedfrom the primary electronic device 102D that indicates that thesecondary electronic device 102A can start transmitting training frames(904). Upon receiving a training frame from the primary electronicdevice 102D that indicates that the secondary electronic device 102A canstart transmitting training frames (904), the secondary electronicdevice 102A transmits a training sequence to the primary electronicdevice 102D (906), e.g. using the training frame format discussedfurther below with respect to FIG. 11, the information field formatsdiscussed further below with respect to FIG. 12, and/or the secondaryelectronic device 102A message identifier values discussed further belowwith respect to FIG. 14.

The secondary electronic device 102A waits for the convergence of itsreceiver (indicating the same to the primary electronic device 102D viathe aforementioned training sequence), and waits for a training frameindicating that the receiver of the primary electronic device 102D hasconverged (908). The secondary electronic device 102A receives atraining frame from the primary electronic device 102D that includesscrambler initialization information for the scrambler 236 of theprimary electronic device 102D, such as a scrambler seed, and anothertraining frame that includes primary device data mode timing informationindicating a time that the primary electronic device 102D willinitialize its scrambler 236 and enter the data mode (910).

The secondary electronic device 102A transmits a training frame thatincludes scrambler initialization information for its scrambler, such asa scrambler seed, and another training frame that includes secondarydevice data mode timing information indicating a time that the secondaryelectronic device 102A will initialize its scrambler and enter the datamode (912). The secondary electronic device 102A initializes itsscrambler with the secondary device scrambler initialization informationat the indicated time and switches to the data mode (914). The secondaryelectronic device 102A initializes its descrambler with the receivedprimary device scrambler initialization information at the timeindicated by the primary electronic device 102D (916). The secondaryelectronic device 102A transmits and receives data with the primaryelectronic device 102D using its initialized scrambler and descrambler(918).

FIG. 10 illustrates an example timing diagram 1000 for linkestablishment for single pair Ethernet in accordance with one or moreimplementations. For explanatory purposes, the example timing diagram1000 is described herein with reference to the electronic devices 102A,Dof FIG. 1; however, the example timing diagram 1000 is not limited tothe electronic devices 102A,D of FIG. 1, and the example timing diagram1000 may be performed by one or more components of one or more of theelectronic devices 102A,D. Further for explanatory purposes, the blocksof the example timing diagram 1000 are described herein as occurring inserial, or linearly. However, multiple blocks of the example timingdiagram 1000 may occur in parallel. In addition, the blocks of theexample timing diagram 1000 need not be performed in the order shownand/or one or more of the blocks of the example timing diagram 1000 neednot be performed.

When the PHY module 220 of the primary electronic device 102D isenabled, the primary electronic device 102D enters the synchronizationstage by transmitting its synchronization sequence (1001). When the PHYof the secondary electronic device 102A is enabled, the secondaryelectronic device 102A enters the synchronization stage by transmittingzeros (1002, 1004). Upon completing the transmission of itssynchronization sequence (1001), the primary electronic device 102Dtransmits zeros (1003, 1005). During this time the secondary electronicdevice 102A transmits its synchronization sequence (1006). Bothelectronic devices 102A,D then transmit zeros for a preconfiguredduration of time (1007, 1008), and enter the training stagesynchronously.

The primary electronic device 102D initiates the training stage bytransmitting its training sequence (1009). The secondary electronicdevice 102A transmits zeros (1010) until it receives an indication fromthe primary electronic device 102D that it may begin transmittingtraining frames (1011). At that time, the secondary electronic device102A begins transmitting its training sequence (1012). Both electronicdevices 102A,D wait for their respective receivers, and each other'sreceiver, to converge (1013, 1014). The electronic devices 102A,D thenexchange scrambler initialization information and data mode timinginformation for initializing the respective scramblers and entering thedata mode (1015, 1016). In one or more implementations, the timinginformation may include a counter value, or a countdown value, thatindicates when the respective electronic devices 102A,D will initializetheir respective scramblers and enter the data mode.

The electronic devices 102A,D enter the data mode in accordance with theprovided, and received, data mode timing information (1017, 1018). Forexample, the primary electronic device 102D may initialize the scrambler236 and enter the data mode at the time indicated by the data modetiming information provided to the secondary electronic device 102A, andthe primary electronic device 102D may initialize the descrambler 246 atthe time indicated by the data mode timing information received from thesecondary electronic device 102A. The electronic devices 102A,D thenenter the data mode and transmit data, e.g. using the initializedscramblers (1019-1022).

FIG. 11 illustrates an example frame format 1100 for the training stageof link establishment for single pair Ethernet in accordance with one ormore implementations. Not all of the depicted components may berequired, however, and one or more implementations may includeadditional components not shown in the figure. Variations in thearrangement and type of the components may be made without departingfrom the spirit or scope of the claims as set forth herein. Additionalcomponents, different components, or fewer components may be provided.

The example frame format 1100 illustrates a training frame, such as aPAM2 training frame. The frame format includes a one bit inversion 1102every 240 nanoseconds, or every 180 PAM2 symbols. The training frame is3.6 microseconds and is aligned with a data mode FEC frame. Eachtraining frame includes a 96-bit information field 1104 at the end ofthe frame. An example format of the information field 1104 is discussedfurther below with respect to FIG. 12, example information fieldmessages of a primary electronic device 102D are discussed further belowwith respect to FIG. 13, and example information field messages of asecondary electronic device 102A are discussed further below withrespect to FIG. 14.

FIG. 12 illustrates example information field formats 1210-1240 for thetraining stage of link establishment for single pair Ethernet inaccordance with one or more implementations. Not all of the depictedcomponents may be required, however, and one or more implementations mayinclude additional components not shown in the figure. Variations in thearrangement and type of the components may be made without departingfrom the spirit or scope of the claims as set forth herein. Additionalcomponents, different components, or fewer components may be provided.

Messages formatted using the information field formats 1210-1240 eachlasts at least 256 frames (less than 1 microsecond) to ensure detectionby the link partner. The information field formats 1210-1240 include a24-bit partial RS frame count (PFC) value 1202 that is incremented by 15(or 24) per frame to avoid wrap-around ambiguity. That is, with a 24-bitPFC it takes less than four seconds without counter wrap-around (2²⁴*3.6microseconds/15=4.0265 seconds). The information field formats 1210-1240each include an eight bit message identifier 1204 that is used toindicate the type of data, if any, carried in the four subsequentoctets, and to transition through the PAM2 training states. Examplevalues of the message identifier 1204 for a primary electronic device102D are discussed further below with respect to FIG. 13 and examplevalues for the message identifier 1204 of a secondary electronic device102A are discussed further below with respect to FIG. 14.

The general information field format 1210 includes three message octets1205 that can be used to transmit any type of data, such as data modecapabilities, optional parameters, and/or scrambler initializationinformation. For example, in the scrambler information field format 1220all three octets are used to transmit scrambler information 1206, suchas the scrambler seed or the initial state of the data mode side-streamscrambler, filling up the 24 least significant bits and assuming thatthe most significant bits (if any) are zero. In the timing informationfield format 1230 all three octets are used to transmit data mode timinginformation 1207, such as the exact time when the device will initializeits scrambler and switch to the data mode. In the vendor specificinformation field format 1240, one of the octets is used to transmit asignal to noise ratio (SNR) 1208 and the other two octets are used totransmit vendor specific information 1209.

FIG. 13 illustrates a table 1300 of example information field messageidentifier 1204 values transmitted by a primary electronic device 102Dduring the training stage of link establishment for single pair Ethernetin accordance with one or more implementations. Not all of the depictedcomponents may be required, however, and one or more implementations mayinclude additional components not shown in the figure. Variations in thearrangement and type of the components may be made without departingfrom the spirit or scope of the claims as set forth herein. Additionalcomponents, different components, or fewer components may be provided.

The table 1300 of example information field message identifier 1204values transmitted by a primary electronic device 102D includes atwo-bit training state identifier 1302 that is used to transitionthrough the training states, such as the PAM2 training states. The table1300 includes a local receiver status bit 1304 which indicates when thelocal receiver has converged. The table 1300 includes an enablesecondary device transmission bit 1306, which is set by the primaryelectronic device 102D to indicate to the secondary electronic device102A when it should start transmitting training frames. The table 1300includes a scrambler seed bit 1308 to indicate when the subsequentoctets will include scrambler initialization information for thescrambler 236 of the primary electronic device 102D, such as a scramblerseed of the primary electronic device 102D, and a scrambler seedacknowledgement bit 1310 to indicate that the primary electronic device102D has received the scrambler initialization information of thesecondary electronic device 102A.

The table 1300 also includes a data mode timing information bit 1312 toindicate when the subsequent octets will include data mode timinginformation, such as an exact time when the primary electronic device102D will initialize the scrambler 236 and enter the data state, and adata mode timing information acknowledgment bit 1314 to indicate thatthe primary electronic device 102D has received the data mode timinginformation of the secondary electronic device 102A, e.g. the time whenthe primary electronic device 102D should initialize the descrambler 246with the scrambler initialization information received from thesecondary electronic device 102A. In one or more implementations thetiming information is relative to, and/or in terms of, the 24-bit PFCvalue 1202, such as a PFC counter value. Thus, the primary electronicdevice 102D initializes the descrambler 246 with the received scramblerinitialization information at the beginning, or end, of the specifiedPFC count.

FIG. 14 illustrates a table 1400 of example information field messageidentifier 1204 values transmitted by a secondary electronic device 102Aduring the training stage of link establishment for single pair Ethernetin accordance with one or more implementations. Not all of the depictedcomponents may be required, however, and one or more implementations mayinclude additional components not shown in the figure. Variations in thearrangement and type of the components may be made without departingfrom the spirit or scope of the claims as set forth herein. Additionalcomponents, different components, or fewer components may be provided.

The table 1400 of example information field message identifier 1204values transmitted by a secondary electronic device 102A includes atwo-bit training state identifier 1402 that is used to transitionthrough the training states, such as the PAM2 training states. The table1400 includes a local receiver status bit 1404 which indicates when thelocal receiver has converged. The table 1400 includes a timing lock bit1406 which is set to indicate timing convergence. The table 1400includes a scrambler seed bit 1408 to indicate when the subsequentoctets will include scrambler initialization information for thescrambler of the secondary electronic device 102A, such as a scramblerseed of the secondary electronic device 102A, and a scrambler seedacknowledgement bit 1410 to indicate that the secondary electronicdevice 102A has received the scrambler initialization information of theprimary electronic device 102D.

The table 1400 also includes a data mode timing information bit 1412 toindicate when the subsequent octets will include data mode timinginformation, such as an exact time when the secondary electronic device102A will initialize its scrambler and enter the data state, and a datamode timing information acknowledgment bit 1414 to indicate that thesecondary electronic device 102A has received the data mode timinginformation of the primary electronic device 102D, e.g. the time whenthe secondary electronic device 102A should initialize its descramblerwith the scrambler initialization information received from the primaryelectronic device 102D. In one or more implementations the data modetiming information is relative to, and/or in terms of, the 24-bit PFCvalue 1202, such as a PFC counter value. Thus, the secondary electronicdevice 102A initializes its descrambler with the received scramblerinitialization information at the beginning, or end, of the specifiedPFC count.

FIG. 15 illustrates an example bit ordering 1500 of a physical codingsublayer (PCS) transmit module 230 in accordance with one or moreimplementations. Not all of the depicted components may be required,however, and one or more implementations may include additionalcomponents not shown in the figure. Variations in the arrangement andtype of the components may be made without departing from the spirit orscope of the claims as set forth herein. Additional components,different components, or fewer components may be provided.

The example bit ordering 1500 begins with 80-bit data blocks 1510 thatare appended with a header and encoded to 81-bit data blocks 1520 by thePCS encoder 232. Forty-five 81-bit data blocks plus a 9-bit operations,administration, and maintenance (OAM) block are aggregated to form theRS encoder 234 payloads 1530. The RS encoder 234 generates RS symbols1540 (or codewords) from the payloads. The scrambler 236 performs an XORoperation on the RS symbols 1540 and the scrambler sequence and outputsthe scrambled data blocks to the signal mapper 238. Thus, the OAM blocks(in addition to the data blocks) are encoded by the RS encoder 234 andscrambled by the scrambler 236. The signal mapper 238 maps three bits ofthe scrambled data blocks to two ternary symbols to generate the PAMsymbols 1550.

FIG. 16 further illustrates an example bit ordering 1600 of a physicalcoding sublayer (PCS) transmit module 230 in accordance with one or moreimplementations. Not all of the depicted components may be required,however, and one or more implementations may include additionalcomponents not shown in the figure. Variations in the arrangement andtype of the components may be made without departing from the spirit orscope of the claims as set forth herein. Additional components,different components, or fewer components may be provided.

The example bit ordering 1600 includes the data blocks 1610 that areoutput by the PCS encoder 232 and are mapped to the RS symbols 1620 thatare output by the RS encoder 234. The RS symbols 1620 are over a GaloisField (GF) of 2⁹, i.e. b₈α⁸+b₇α⁷+b₆α⁶+ . . . +b₁α+b₀. The RS symbols1620 are XOR'd with the scrambler sequence generated by the scrambler236 to generate the scrambled data blocks 1630. The scrambled datablocks 1630 are mapped to ternary symbols 1640 by the signal mapper 238.

FIG. 17 illustrates an example bit ordering 1700 of a physical codingsublayer (PCS) receive module 240 in accordance with one or moreimplementations. Not all of the depicted components may be required,however, and one or more implementations may include additionalcomponents not shown in the figure. Variations in the arrangement andtype of the components may be made without departing from the spirit orscope of the claims as set forth herein. Additional components,different components, or fewer components may be provided.

The example bit ordering 1700 begins with a received signal 1710 that isframe synchronized to produce PAM symbols 1720. The signal demapper 248demaps the PAM symbols to scrambled data blocks which are XOR'd by thedescrambler 246 with the link partner's scramble sequence to produce theRS symbols 1730. The RS decoder 244 decodes the RS symbols 1730 toobtain the aggregated data blocks that include forty-five 81-bit datablocks plus the 9-bit OAM block 1740. The OAM block is extracted fromthe aggregated data blocks 1740 and the remaining data blocks areseparated into 81-bit bocks 1750. The PCS decoder 242 removes the headerto decode the 81-bit blocks to 80-bit blocks 1760.

FIG. 18 conceptually illustrates an electronic system 1800 with whichone or more implementations of the subject technology may beimplemented. The electronic system 1800, for example, may be, or may becoupled to, a powertrain system, a chassis system, a telematics system,an entertainment system, a camera system, a sensor system, such as alane departure system, a diagnostics system, a gateway device, a set-topbox, a desktop computer, a laptop computer, a tablet computer, a server,a switch, a router, a base station, a receiver, a phone, a personaldigital assistant (PDA), or generally any electronic device thattransmits signals over a network. The electronic system 1800 can be,and/or can be a part of, one or more of the electronic devices 102A-D.Such an electronic system includes various types of computer readablemedia and interfaces for various other types of computer readable media.The electronic system 1800 includes a bus 1808, one or more processor(s)1812, a system memory 1804 or buffer, a read-only memory (ROM) 1810, apermanent storage device 1802, an input device interface 1814, an outputdevice interface 1806, and one or more network interface(s) 1816, orsubsets and variations thereof.

The bus 1808 collectively represents all system, peripheral, and chipsetbuses that communicatively connect the numerous internal devices of theelectronic system 1800. In one or more implementations, the bus 1808communicatively connects the one or more processor(s) 1812 with the ROM1810, the system memory 1804, and the permanent storage device 1802.From these various memory units, the one or more processor(s) 1812retrieve instructions to execute and data to process in order to executethe processes of the subject disclosure. The one or more processor(s)1812 can be a single processor or a multi-core processor in differentimplementations.

The ROM 1810 stores static data and instructions that are needed by theone or more processor(s) 1812 and other modules of the electronic system1800. The permanent storage device 1802, on the other hand, may be aread-and-write memory device. The permanent storage device 1802 may be anon-volatile memory unit that stores instructions and data even when theelectronic system 1800 is off. In one or more implementations, amass-storage device (such as a magnetic or optical disk and itscorresponding disk drive) may be used as the permanent storage device1802.

In one or more implementations, a removable storage device (such as afloppy disk, flash drive, and its corresponding disk drive) may be usedas the permanent storage device 1802. Like the permanent storage device1802, the system memory 1804 may be a read-and-write memory device.However, unlike the permanent storage device 1802, the system memory1804 may be a volatile read-and-write memory, such as random accessmemory. The system memory 1804 may store any of the instructions anddata that one or more processor(s) 1812 may need at runtime. In one ormore implementations, the processes of the subject disclosure are storedin the system memory 1804, the permanent storage device 1802, and/or theROM 1810. From these various memory units, the one or more processor(s)1812 retrieve instructions to execute and data to process in order toexecute the processes of one or more implementations.

The bus 1808 also connects to the input and output device interfaces1814 and 1806. The input device interface 1814 enables a user tocommunicate information and select commands to the electronic system1800. Input devices that may be used with the input device interface1814 may include, for example, alphanumeric keyboards and pointingdevices (also called “cursor control devices”). The output deviceinterface 1806 may enable, for example, the display of images generatedby the electronic system 1800. Output devices that may be used with theoutput device interface 1806 may include, for example, printers anddisplay devices, such as a liquid crystal display (LCD), a lightemitting diode (LED) display, an organic light emitting diode (OLED)display, a flexible display, a flat panel display, a solid statedisplay, a projector, or any other device for outputting information.One or more implementations may include devices that function as bothinput and output devices, such as a touchscreen. In theseimplementations, feedback provided to the user can be any form ofsensory feedback, such as visual feedback, auditory feedback, or tactilefeedback; and input from the user can be received in any form, includingacoustic, speech, or tactile input.

As shown in FIG. 18, the bus 1808 also couples the electronic system1800 to one or more networks (not shown), and/or one or more of theelectronic devices 102A-D, through one or more network interface(s)1816. One or more network interface(s) may include an Ethernetinterface, a WIFI interface, a multimedia over coax alliance (MoCA)interface, a reduced gigabit media independent interface (RGMII), orgenerally any interface for connecting to a network. The one or morenetwork interfaces 1816 may include, or may be coupled to, a physicallayer module, such as the PHY module 220. In this manner, the electronicsystem 1800 can be a part of one or more networks of computers (such asa local area network (“LAN”), a wide area network (“WAN”), or anIntranet, or a network of networks, such as the Internet. Any or allcomponents of the electronic system 1800 can be used in conjunction withthe subject disclosure.

Implementations within the scope of the present disclosure can bepartially or entirely realized using a tangible computer-readablestorage medium (or multiple tangible computer-readable storage media ofone or more types) encoding one or more instructions. The tangiblecomputer-readable storage medium also can be non-transitory in nature.

The computer-readable storage medium can be any storage medium that canbe read, written, or otherwise accessed by a general purpose or specialpurpose computing device, including any processing electronics and/orprocessing circuitry capable of executing instructions. For example,without limitation, the computer-readable medium can include anyvolatile semiconductor memory, such as RAM, DRAM, SRAM, T-RAM, Z-RAM,and TTRAM. The computer-readable medium also can include anynon-volatile semiconductor memory, such as ROM, PROM, EPROM, EEPROM,NVRAM, flash, nvSRAM, FeRAM, FeTRAM, MRAM, PRAM, CBRAM, SONOS, RRAM,NRAM, racetrack memory, FJG, and Millipede memory.

Further, the computer-readable storage medium can include anynon-semiconductor memory, such as optical disk storage, magnetic diskstorage, magnetic tape, other magnetic storage devices, or any othermedium capable of storing one or more instructions. In someimplementations, the tangible computer-readable storage medium can bedirectly coupled to a computing device, while in other implementations,the tangible computer-readable storage medium can be indirectly coupledto a computing device, e.g., via one or more wired connections, one ormore wireless connections, or any combination thereof.

Instructions can be directly executable or can be used to developexecutable instructions. For example, instructions can be realized asexecutable or non-executable machine code or as instructions in ahigh-level language that can be compiled to produce executable ornon-executable machine code. Further, instructions also can be realizedas or can include data. Computer-executable instructions also can beorganized in any format, including routines, subroutines, programs, datastructures, objects, modules, applications, applets, functions, etc. Asrecognized by those of skill in the art, details including, but notlimited to, the number, structure, sequence, and organization ofinstructions can vary significantly without varying the underlyinglogic, function, processing, and output.

While the above discussion primarily refers to microprocessor ormulti-core processors that execute software, one or more implementationsare performed by one or more integrated circuits, such as applicationspecific integrated circuits (ASICs) or field programmable gate arrays(FPGAs). In one or more implementations, such integrated circuitsexecute instructions that are stored on the circuit itself.

Those of skill in the art would appreciate that the various illustrativeblocks, modules, elements, components, methods, and algorithms describedherein may be implemented as electronic hardware, computer software, orcombinations of both. To illustrate this interchangeability of hardwareand software, various illustrative blocks, modules, elements,components, methods, and algorithms have been described above generallyin terms of their functionality. Whether such functionality isimplemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system.Skilled artisans may implement the described functionality in varyingways for each particular application. Various components and blocks maybe arranged differently (e.g., arranged in a different order, orpartitioned in a different way) all without departing from the scope ofthe subject technology.

It is understood that any specific order or hierarchy of blocks in theprocesses disclosed is an illustration of example approaches. Based upondesign preferences, it is understood that the specific order orhierarchy of blocks in the processes may be rearranged, or that allillustrated blocks be performed. Any of the blocks may be performedsimultaneously. In one or more implementations, multitasking andparallel processing may be advantageous. Moreover, the separation ofvarious system components in the embodiments described above should notbe understood as requiring such separation in all embodiments, and itshould be understood that the described program components and systemscan generally be integrated together in a single software product orpackaged into multiple software products.

As used in this specification and any claims of this application, theterms “base station”, “receiver”, “computer”, “server”, “processor”, and“memory” all refer to electronic or other technological devices. Theseterms exclude people or groups of people. For the purposes of thespecification, the terms “display” or “displaying” means displaying onan electronic device.

As used herein, the phrase “at least one of” preceding a series ofitems, with the term “and” or “or” to separate any of the items,modifies the list as a whole, rather than each member of the list (i.e.,each item). The phrase “at least one of” does not require selection ofat least one of each item listed; rather, the phrase allows a meaningthat includes at least one of any one of the items, and/or at least oneof any combination of the items, and/or at least one of each of theitems. By way of example, the phrases “at least one of A, B, and C” or“at least one of A, B, or C” each refer to only A, only B, or only C;any combination of A, B, and C; and/or at least one of each of A, B, andC.

The predicate words “configured to”, “operable to”, and “programmed to”do not imply any particular tangible or intangible modification of asubject, but, rather, are intended to be used interchangeably. In one ormore implementations, a processor configured to monitor and control anoperation or a component may also mean the processor being programmed tomonitor and control the operation or the processor being operable tomonitor and control the operation. Likewise, a processor configured toexecute code can be construed as a processor programmed to execute codeor operable to execute code.

Phrases such as an aspect, the aspect, another aspect, some aspects, oneor more aspects, an implementation, the implementation, anotherimplementation, some implementations, one or more implementations, anembodiment, the embodiment, another embodiment, some embodiments, one ormore embodiments, a configuration, the configuration, anotherconfiguration, some configurations, one or more configurations, thesubject technology, the disclosure, the present disclosure, othervariations thereof and alike are for convenience and do not imply that adisclosure relating to such phrase(s) is essential to the subjecttechnology or that such disclosure applies to all configurations of thesubject technology. A disclosure relating to such phrase(s) may apply toall configurations, or one or more configurations. A disclosure relatingto such phrase(s) may provide one or more examples. A phrase such as anaspect or some aspects may refer to one or more aspects and vice versa,and this applies similarly to other foregoing phrases.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any embodiment described herein as“exemplary” or as an “example” is not necessarily to be construed aspreferred or advantageous over other embodiments. Furthermore, to theextent that the term “include,” “have,” or the like is used in thedescription or the claims, such term is intended to be inclusive in amanner similar to the term “comprise” as “comprise” is interpreted whenemployed as a transitional word in a claim.

All structural and functional equivalents to the elements of the variousaspects described throughout this disclosure that are known or latercome to be known to those of ordinary skill in the art are expresslyincorporated herein by reference and are intended to be encompassed bythe claims. Moreover, nothing disclosed herein is intended to bededicated to the public regardless of whether such disclosure isexplicitly recited in the claims. No claim element is to be construedunder the provisions of 35 U.S.C. § 112, sixth paragraph, unless theelement is expressly recited using the phrase “means for” or, in thecase of a method claim, the element is recited using the phrase “stepfor.”

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but are to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. Pronouns in themasculine (e.g., his) include the feminine and neuter gender (e.g., herand its) and vice versa. Headings and subheadings, if any, are used forconvenience only and do not limit the subject disclosure.

What is claimed is:
 1. A primary device comprising: at least oneprocessor configured to: transmit a first synchronization sequence to asecondary device; detect a second synchronization sequence transmittedby the secondary device, the second synchronization sequence differingfrom the first synchronization sequence; after detection of the secondsynchronization sequence, initiate a training stage, the training stagecomprising transmitting training frames to the secondary device; andenter a data mode for data transmissions after completion of thetraining stage, the data transmissions comprising different content thanthe training frames.
 2. The primary device of claim 1, wherein the atleast one processor is configured to wait a first predetermined amountof time after detection of the second synchronization sequence beforeinitiation of the training stage.
 3. The primary device of claim 2,wherein the at least one processor is further configured to: retransmitthe first synchronization sequence to the secondary device when thesecond synchronization sequence is not detected after a secondpredetermined amount of time; and transmit zeros after transmitting thefirst synchronization sequence and while waiting for the firstpredetermined amount of time.
 4. The primary device of claim 1, whereinthe first and second synchronization sequences comprise pseudo-noisesequences that are detectable under at least one of narrow bandinterference (NBI) or burst noise conditions.
 5. The primary device ofclaim 1, wherein the at least one processor, when in the training stage,is configured to: transmit primary device scrambler initializationinformation to the secondary device, and receive secondary devicescrambler initialization information from the secondary device; transmitprimary device data mode timing information to the secondary device, andreceive secondary device data mode timing information from the secondarydevice; initialize a scrambler based at least in part on the primarydevice scrambler initialization information and at a first timeindicated by the primary device data mode timing information; andinitialize a descrambler based at least in part on the receivedsecondary device scrambler initialization information and at a secondtime indicated by the received secondary device data mode timinginformation.
 6. The primary device of claim 5, wherein the at least oneprocessor is further configured to: perform Reed-Solomon (RS) encodingon data for transmission; subsequently scramble the encoded data usingthe initialized scrambler; signal map the scrambled data to generatesymbols; and transmit the symbols to the secondary device.
 7. Theprimary device of claim 6, wherein the data for transmission comprisesan operations, administration, and maintenance (OAM) block that issubsequently RS encoded and scrambled.
 8. The primary device of claim 5,wherein the at least one processor is further configured to: signaldemap data received from the secondary device; perform Reed-Solomon (RS)decoding on the demapped data; and subsequently descramble the RSdecoded data using the initialized descrambler.
 9. The primary device ofclaim 5, wherein the first time differs from the second time.
 10. Theprimary device of claim 1, wherein the training stage is a two-levelpulse amplitude modulation (PAM2) training stage and, when in thetraining stage, the at least one processor is configured to: receiveother training frames from the secondary device, wherein each of theother training frames comprises an information field that indicatesstate transitions for the training stage and a partial Reed Solomon (RS)frame count that is used to determine when to enter the data mode.
 11. Amethod comprising: at a secondary device: detecting a firstsynchronization sequence transmitted by a primary device, transmitting asecond synchronization sequence that differs from the firstsynchronization sequence after detecting the first synchronizationsequence, after completion of transmission of the second synchronizationsequence, waiting a predetermined amount of time and then immediatelyentering a training stage, the training stage comprising exchangingtraining frames with the primary device, and entering a data mode fordata transmissions after completion of the training stage, the datatransmissions being distinct from the training frames, wherein thetraining frames comprise a training frame format that differs from aframe format of the data transmissions.
 12. The method of claim 11,wherein the first and second synchronization sequences comprisepseudo-noise sequences that are detectable under at least one of narrowband interference (NBI) or burst noise conditions.
 13. The method ofclaim 11, wherein the training stage comprises: waiting for the primarydevice to provide an indication that transmission of the training framesmay begin; upon receiving the indication, transmitting secondary devicescrambler initialization information and secondary device data modetiming information to the primary device; receiving primary devicescrambler initialization information and primary device data mode timinginformation from the primary device; initializing a scrambler based atleast in part on the secondary device scrambler initializationinformation and at a first time indicated by the secondary device datamode timing information; and initializing a descrambler based at leastin part on the received primary device scrambler initializationinformation and at a second time indicated by the primary device datamode timing information.
 14. The method of claim 13, wherein the firsttime differs from the second time.
 15. The method of claim 11, whereinthe training stage is a two-level pulse amplitude modulation (PAM2)training stage, and the training stage comprises: exchanging thetraining frames with the primary device, wherein each training framecomprises an information field that indicates state transitions for thetraining stage and a partial Reed Solomon (RS) frame count that is usedto determine when to enter the data mode.
 16. The method of claim 15,further comprising: exchanging scrambler initialization information anddata mode timing information with the primary device via the informationfields of the training frames.
 17. A computer program product comprisinginstructions stored in a non-transitory computer-readable storagemedium, the instructions comprising: instructions to synchronize with asecondary device and entering a training stage synchronously with thesecondary device, wherein the training stage comprises a plurality ofstates; instructions to exchange training frames with the secondarydevice to exchange scrambler initialization information and data modetiming information with the secondary device, wherein an informationfield of each of the training frames indicates one of the plurality ofstates of the training stage; instructions to initialize a scramblerusing the scrambler initialization information provided to the secondarydevice and at a first time indicated by the data mode timing informationprovided to the secondary device; instructions to initialize adescrambler using received scrambler initialization information obtainedfrom the secondary device and at a second time indicated by receiveddata mode timing information obtained from the secondary device; andinstructions to enter a data mode for data transmissions, the datatransmissions being distinct from the training frames.
 18. The computerprogram product of claim 17, wherein the data mode comprises:instructions to perform Reed-Solomon (RS) encoding on data fortransmission; instructions to subsequently scramble the RS encoded datausing the initialized scrambler; instructions to signal map thescrambled data to generate symbols; and instructions to transmit thesymbols to the secondary device.
 19. The computer program product ofclaim 18, wherein the data for transmission comprises an operations,administration, and maintenance (OAM) block that is subsequently RSencoded and scrambled.
 20. The computer program product of claim 17,wherein the data mode comprises: instructions to signal demap datareceived from the secondary device; instructions to perform Reed-Solomon(RS) decoding on the demapped data; and instructions to subsequentlydescramble the RS decoded data using the initialized descrambler.